deployment: add mainnet native config override layer#14628
Draft
nimrod-starkware wants to merge 1 commit into
Draft
deployment: add mainnet native config override layer#14628nimrod-starkware wants to merge 1 commit into
nimrod-starkware wants to merge 1 commit into
Conversation
This was referenced Jun 25, 2026
Contributor
Author
This was referenced Jun 25, 2026
|
This change is |
nimrod-starkware
force-pushed
the
nimrod/jsonnet/native-override-mainnet
branch
from
652ee03 to
2e11c32
Compare
nimrod-starkware
force-pushed
the
nimrod/jsonnet/native-override-alpha
branch
from
da1af43 to
52a1181
Compare
This was referenced Jun 28, 2026
Draft
nimrod-starkware
force-pushed
the
nimrod/jsonnet/native-override-alpha
branch
from
52a1181 to
cc2b14f
Compare
nimrod-starkware
force-pushed
the
nimrod/jsonnet/native-override-mainnet
branch
from
2e11c32 to
aa981cd
Compare
nimrod-starkware
force-pushed
the
nimrod/jsonnet/native-override-mainnet
branch
from
aa981cd to
cfcf68f
Compare
Translate the mainnet config.sequencerConfig overrides (the public common.yaml + services/*.yaml flat dotted keys) into the nested sequencer_config.jsonnet override layer the native config builder consumes, mirroring the existing sepolia-integration and sepolia-alpha layers. Add a regression test asserting the jsonnet layer stays in lockstep with the combined YAML overrides (folded: Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
nimrod-starkware
force-pushed
the
nimrod/jsonnet/native-override-mainnet
branch
from
cfcf68f to
ab93940
Compare
nimrod-starkware
force-pushed
the
nimrod/jsonnet/native-override-alpha
branch
from
2c6cc65 to
977e2c8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Translate the mainnet config.sequencerConfig overrides (the public common.yaml +
services/*.yaml flat dotted keys) into the nested sequencer_config.jsonnet
override layer the native config builder consumes, mirroring the existing
sepolia-integration and sepolia-alpha layers. Add a regression test asserting
the jsonnet layer stays in lockstep with the combined YAML overrides (folded:
#is_none applied, components dropped).
Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com